Suppressing custom code during GCF operations

Some of the standard Meridian Enterprise events occur during GCF import and export operations. In the following lists, an asterisk (*) is used for brevity but indicates that there are separate Initiate, Before, After, and Terminate events that are otherwise named the same:

• Briefcase events

BrcEvent_BeforeInclude
BrcEvent_AfterInclude
BrcEvent_BeforeWriteProperty
BrcEvent_BeforeImport
BrcEvent_AfterImport
BrcEvent_AfterReadProperty
BrcEvent_Before_Create
BrcEvent_BeforeOpen
BrcEvent_AfterOpen
BrcEvent_BeforeClose

• Other events

DocWorkingCopyEvent_*CreateWC
DocWorkingCopyEvent_*SubmitWC
DocWorkflowEvent_*ChangeWFPerson

• Work area events

DocWorkAreaEvent_*Assign
DocWorkAreaEvent_*Cancel
DocWorkAreaEvent_*Release

To skip the execution of your custom code (if any) during these events so that it doesn't interfere with Global Collaboration Framework processing, add the following line to the top of the corresponding event handler procedures:

If Vault.Argument("IsGcf") then Exit Sub

Notes

• The name of the argument is case-sensitive.
• The same modification should be made to any custom .NET user interface extensions if they implement handlers for the preceding events. In that case, the GcfEvents extension should be moved to the top of the list of .NET extensions applied to a document type as described in theBlueCielo Meridian Enterprise Configuration Guide.